Fix Selenium packaging in Windows executable - #6

The Windows executable failed before browser startup with No module named 'selenium.webdriver.chrome.options'. Selenium loads WebDriver modules dynamically, and the previous build commands did not bundle the complete dependency.

Use one canonical PyInstaller spec to collect Selenium modules and runtime data, including Selenium Manager. Validate lazy imports at startup, stop retrying a missing dependency, and give packaged users rebuild/download guidance instead of telling them to run pip inside the EXE.

Add Aeyori.exe --check-bundle report.json to verify the actual shipped runtime without opening the UI or contacting external services. Document this release check and add two regression tests for frozen/source dependency failures.

Validation:

• Both missing-dependency regression tests pass.
• Patched source opens and closes a headless Chrome session successfully.
• The canonical Windows build completes successfully.
• The generated EXE reports frozen: true and ok: true, including Chrome WebDriver imports and the Selenium Manager binary.

Addresses #5. Leave the issue open pending confirmation with the refreshed download; a source fix alone does not update the release executable.